|
Continuous testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate.〔(Part of the Pipeline: Why Continuous Testing Is Essential ), by Adam Auerbach, TechWell Insights August 2015〕〔(The Relationship between Risk and Continuous Testing: An Interview with Wayne Ariola ), by Cameron Philipp-Edmonds, Stickyminds December 2015〕 For Continuous Testing, the scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals.〔(DevOps: Are You Pushing Bugs to Clients Faster ), by Wayne Ariola and Cynthia Dunlop, PNSQC October 2015〕 ==Adoption drivers== In the 2010s, software has become a key business differentiator.〔(DevOps and QA: What’s the real cost of quality? ), by Ericka Chickowski, DevOps.com June 2015〕 As a result, organizations now expect software development teams to deliver more, and more innovative, software within shorter delivery cycles.〔〔(Kinks persist in Continuous Workflows ), by Lisa Morgan, SD Times September 2014〕 To meet these demands, teams have turned to lean approaches, such as Agile, DevOps, and Continuous Delivery, to try to speed up the SDLC.〔(Continuous Testing: Think Different ), by Ian Davis, Visual Studio Magazine September 2011〕 After accelerating other aspects of the delivery pipeline, teams typically find that their testing process is preventing them from achieving the expected benefits of their SDLC acceleration initiative.〔 Testing and the overall quality process remain problematic for several key reasons.〔 * Traditional testing processes are too slow. Iteration length has changed from months to weeks or days with the rising popularity of Agile, DevOps, and Continuous Delivery. Traditional methods of testing, which rely heavily on manual testing and automated GUI tests that require frequent updating, cannot keep pace.〔〔(The Forrester Wave™ Evaluation Of Functional Test Automation (FTA) Is Out And It's All About Going Beyond GUI Testing ), by Diego Lo Giudice, Forrester Research April 23, 2015〕 At this point, organizations tend to recognize the need to extend their test automation efforts.〔〔(Continuous Development Brings Changes for Software Testers ), by Amy Reichert, SearchSoftwareQuality September 2014〕 * Even after more automation is added to the existing test process, managers still lack adequate insight into the level of risk associated with an application at any given point in time.〔 Understanding these risks is critical for making the rapid go/no go decisions involved in Continuous Delivery processes.〔(Zeichick’s Take: Forget 'Continuous Integration'—the Buzzword is now 'Continuous Testing' ), by Alan Zeichick, SD Times February 2014〕 If tests are developed without an understanding of what the business considers to be an acceptable level of risk, it is possible to have a release candidate that passes all the available tests, but which the business leaders would not consider to be ready for release.〔(Buy the Wrong Software? A Fix Can Cost $700,000 A Conversation with voke’s Theresa Lanowitz ), by Dom Nicastro , CMS Wire October 2014〕 For the test results to accurately indicate whether each release candidate meets business expectations, the approach to designing tests must be based on the business's tolerance for risks related to security, performance, reliability, and compliance.〔 In addition to having unit tests that check code at a very granular bottom-up level, there is a need for a broader suite of tests to provide a top-down assessment of the release candidate's business risk.〔 * Even if testing is automated and tests effectively measure the level of business risk, teams without a coordinated end-to-end quality process tend to have trouble satisfying the business expectations within today's compressed delivery cycles.〔 Trying to remove risks at the end of each iteration has been shown to be significantly slower and more resource-intensive than building quality into the product through defect prevention strategies such as development testing. Organizations adopt Continuous Testing because they recognize that these problems are preventing them from delivering quality software at the desired speed. They recognize the growing importance of software as well as the rising cost of software failure, and they are no longer willing to make a tradeoff between time, scope, and quality.〔〔(Theresa Lanowitz Talks Extreme Test Automation at STAREAST 2014 ), by Beth Romanik, TechWell Insights May 2014〕 〔(Guest View: What’s keeping you from Continuous? ), by Noel Wurst, SD Times November 2015〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「Continuous testing」の詳細全文を読む スポンサード リンク
|